TPUG - Toronto PET Users Group/TPUG Users Group CD/TPUG Users Group CD.iso/C64/C-Communications/(c)c12b.d64/parameters right

Text File | 2007-02-04 | 9KB | 194 lines

3.5.14  mODEM INIT.

tHIS STRING IS A hAYES MODEM COMMAND STRING THAT IS AUTOMATICALLY SENT
TO THE MODEM WHEN nOVATERM FIRST BOOTS UP.  iT IS ALSO SENT WHEN YOU
PRESS c= i IN TERMINAL MODE.  a TYPICAL INITIALIZATION STRING LOOKS
LIKE THIS:

ate1m1q0l2s11=50

tHIS STRING WOULD TURN ECHO ON, TURN ON THE SPEAKER, TURN OFF QUIET
MODE, SET THE SPEAKER VOLUME TO 2, AND SET THE TOUCH TONE SOUND TIME
TO 50 MILLISECONDS.

3.5.15  bAUD RATE.

tHE BAUD RATE IS THE SPEED AT WHICH DATA IS SENT AND RECEIVED OVER THE
MODEM.  nOVATERM CAN OPERATE AT 2400 BAUD UNDER NORMAL CONDITIONS AND
AS HIGH AS 38,400 BAUD USING THE sWIFTlINK-232(TM) CARTRIDGE.  yOU
SELECT THE BAUD RATE FROM A MENU OF AVAILABLE BAUD RATES WHICH IS
LIMITED BY THE MAXIMUM BAUD RATE OF YOUR MODEM.

wITHOUT A sWIFTlINK CARTRIDGE CONNECTED, nOVATERM USES THE rs-232 nmi
ROUTINES FROM THE fEBRUARY 1989 ISSUE OF tRANSACTOR MAGAZINE.  tHESE
ROUTINES PROVIDE CLEAN, RELIABLE COMMUNICATION AT HIGH SPEEDS EVEN
WHEN THE COMPUTER IS SENDING AND RECEIVING DATA AT THE SAME TIME.
tHESE ROUTINES ARE NECESSARY BECAUSE THE rs-232 ROUTINES PRESENT IN
THE STOCK cOMMODORE 64 DO NOT WORK PROPERLY BEYOND 300 BAUD.  tHE
tRANSACTOR ROUTINES USE CAREFULLY SELECTED VALUES FOR START-BIT AND
FULL-BIT TRANSMISSION TIMES TO OVERCOME THE ERRORS.  tHESE "TIMES" ARE
ACTUALLY VALUES USED BY AN INTERNAL COUNTER TO DETERMINE WHEN THE NEXT
BIT OF DATA SHOULD BE SENT OR RECEIVED.  eACH BYTE OF DATA HAS EIGHT
BITS WHICH MUST BE SENT PLUS A STARTING BIT WHICH PRECEDES IT.  tHE
START BIT TAKES SLIGHTLY LONGER TO SEND THAN THE BITS OF REAL DATA
(CALLED "FULL BITS") AND THUS THE START-BIT TIME IS LONGER THAN THE
FULL-BIT TIME.

3.5.16  dIAL METHOD.  sEE SECTION 2.3.7.

3.5.17  rEDIAL TIME.

dURING EACH ATTEMPT AT AUTODIALING, nOVATERM WAITS A CERTAIN NUMBER OF
SECONDS BEFORE GIVING UP WITHOUT A CONNECTION.  tHAT AMOUNT OF TIME IS
SET HERE.

3.5.18  xoff CHAR, xon CHAR.

tHESE ARE SINGLE ascii CHARACTERS USED TO PAUSE AND RESUME
TRANSMISSION.  uSUALLY, xoff IS THE CTRL-s KEY (ascii 19) AND xon IS
CTRL-q (ascii 17) (THESE ARE nOVATERM'S DEFAULTS), BUT THEY MAY VARY
AMONG BULLETIN BOARDS (FOR EXAMPLE, SOME bbs'S USE p TO PAUSE AND ANY
OTHER KEY TO CONTINUE).  tHE ascii VALUES OF THE CHARACTERS USED BY
nOVATERM ARE DISPLAYED.  wHEN YOU CHOOSE TO MODIFY EITHER OF THESE,
TYPE THE ACTUAL CHARACTER TO BE USED, NOT THE ascii VALUE.

3.5.19  fLOW CONTROL TOLERANCE.  sEE SECTION 3.5.25.

3.5.20  pROTOCOL BLOCK SIZE.

kERMIT AND pUNTER PROTOCOLS ALLOW A VARIABLE BLOCK SIZE (SEE SECTION
3.5.2, pROTOCOLS).  tHIS OPTION ALLOWS THE BLOCK SIZE TO BE SET WITHIN
AN ACCEPTABLE RANGE.  tHE VALUE HERE MAY NOT BE CHANGED WHEN ONE OF
THE OTHER PROTOCOLS (xMODEM, xMODEM-1K, yMODEM BATCH) IS IN MEMORY.

3.5.21  bATCH DOWNLOAD FILE TYPE.

dURING A yMODEM BATCH OR kERMIT DOWNLOAD, THERE IS NO MEANS OF
SPECIFYING THE FILE TYPE WHILE THE TRANSFER IS TAKING PLACE.  iNSTEAD
OF SIMPLY SAVING THESE DOWNLOADS AS "PRG" FILES, THE FILE TYPE OF
BATCH-DOWNLOADED FILES MAY BE SET TO "PRG", "SEQ", OR "USR" WITH THIS
OPTION.  iF THIS IS SET TO "SEQ", THE FILE TYPE OF EVERY FILE
DOWNLOADED USING yMODEM BATCH OR kERMIT WILL BE "SEQ", AND LIKEWISE
WITH "PRG" AND "USR".  tHIS SETTING HAS NO EFFECT WITH mULTI-pUNTER,
SINCE pUNTER PROTOCOL SENDS THE FILE TYPE OF TRANSFERRED FILES.

3.5.22  cOMM PARAMETERS.

sOME BULLETIN BOARDS OR MAINFRAMES MAY USE ONLY SEVEN OF THE EIGHT
BITS OF A BYTE FOR COMMUNICATION.  tO ACCOMODATE FOR THIS, YOU MAY USE
EITHER 8 BITS WITH NO PARITY, 7 BITS WITH EVEN PARITY, OR 7 BITS WITH
ODD PARITY.  mOST SYSTEMS USE 8 BITS WITH NO PARITY.

3.5.23  bELL.

tHIS SIMPLY TURNS THE BELL ON OR OFF.

3.5.24  sAVE BUFFER WHEN FULL.

mORE THAN 8192 BYTES OF TEXT MAY BE CAPTURED AND SAVED TO DISK WITHOUT
RUNNING OUT OF MEMORY, EVEN THOUGH THE BUFFER IS RESTRICTED TO THAT
SIZE.  wHEN THE BUFFER BECOMES FULL DURING A TEXT CAPTURE, nOVATERM
IMMEDIATELY SENDS A CHARACTER THAT TELLS THE HOST COMPUTER TO PAUSE
(CALLED THE xoff CHARACTER), JUST AS IF YOU HAD PRESSED THE PAUSE KEY.
oNCE THE HOST COMPUTER STOPS SENDING DATA, nOVATERM SAVES THE BUFFER
CAPTURE FILE TO DISK, APPENDING IT TO THE DISK FILE IF IT ALREADY
EXISTS.  tHE CAPTURE FILE IN THE BUFFER IS ERASED AND RE-OPENED,
MAKING ALL THE MEMORY AVAILABLE AGAIN.  tHEN, nOVATERM SENDS A
CHARACTER TO TELL THE HOST TO RESUME TRANSMISSION (THE xon CHARACTER),
ALSO AS IF YOU HAD "HIT A KEY TO CONTINUE" YOURSELF.  tHE BUFFER
CAPTURE CONTINUES AFTER THIS, AND THE PROCESS REPEATS ONCE THE BUFFER
FILLS UP AGAIN.  wHEN THE TEXT YOU WANT TO CAPTURE HAS ALL BEEN
RECEIVED, YOU MUST MANUALLY SAVE THE TEXT REMAINING IN MEMORY.
nOVATERM ALLOWS YOU TO APPEND THE TEXT TO THE EXISTING DISK FILE.
tHIS IS ALL DONE AUTOMATICALLY, BUT IT MAY BE TURNED OFF BY TOGGLING
THIS OPTION.

iF A DISK ERROR OCCURS WHILE TRYING TO SAVE THE CAPTURE FILE, nOVATERM
DOES NOT SEND THE xon CHARACTER TO RESUME TRANSMISSION.  tHIS LEAVES
THE REMOTE SYSTEM PAUSED SO THAT YOU MAY CORRECT THE PROBLEM, SAVE THE
CAPTURE FILE MANUALLY, AND RESUME THE TEXT CAPTURE WHERE IT LEFT OFF.

3.5.25  fLOW CONTROL.

sINCE BOTH 40 AND 80 COLUMN MODES MAY HAVE TROUBLE KEEPING UP WITH
BAUD RATES OF 2400 BAUD AND ABOVE, FLOW CONTROL HAS BEEN IMPLEMENTED
TO PREVENT CHARACTER LOSS.  wHEN THE TERMINAL IS FALLING TOO FAR
BEHIND IN DISPLAYING INCOMING DATA, nOVATERM SENDS A PAUSE (xoff)
CHARACTER TO THE REMOTE COMPUTER. tHIS HALTS TRANSMISSION TO ALLOW
nOVATERM TO CATCH UP.  wHEN THE TERMINAL IS NEARLY CAUGHT UP TO WHERE
IT WAS PAUSED, IT SENDS A CONTINUE (xon) CHARACTER TO RESUME
TRANSMISSION.  tHIS PREVENTS CHARACTERS FROM BEING LOST WHEN nOVATERM
GETS TOO FAR BEHIND THE INCOMING DATA.  tHE FLOW CONTROL IS DONE
AUTOMATICALLY, BUT IT MAY BE TURNED OFF BY TOGGLING THIS OPTION.

a TOLERANCE VALUE FOR THE FLOW CONTROL MAY BE ADJUSTED FROM THE SAME
MENU.  a HIGHER NUMBER MEANS nOVATERM WAITS UNTIL IT IS FURTHER BEHIND
BEFORE SENDING A PAUSE CHARACTER.  tHE DEFAULT IS 150 IN AN ACCEPTABLE
RANGE OF 11 TO 255. gENERALLY, THE HIGHER THE BAUD RATE, THE SMALLER
THIS NUMBER SHOULD BE.  tHIS IS BECAUSE THERE IS A DELAY BETWEEN THE
TIME nOVATERM REALIZES THE BUFFER HAS REACHED ITS TOLERANCE AND THE
TIME nOVATERM SENDS THE PAUSE CHARACTER, DURING WHICH ADDITIONAL DATA
MAY BE RECEIVED AND STORED IN THE BUFFER.

iF YOU ARE OPERATING AT LESS THAN 2400 BAUD, THE FLOW CONTROL
TOLERANCE SHOULDN'T CONCERN YOU AT ALL.  tHE PROBLEM IS MOST COMMON AT
2400 BAUD OR HIGHER IN 80 COLUMN MODE.  iF YOU ARE STILL LOSING A LOT
OF CHARACTERS EVEN WITH FLOW CONTROL TURNED ON, YOU SHOULD DECREASE
THE TOLERANCE UNTIL THE CHARACTER LOSS IS A MINIMUM.  tHIS NUMBER MAY
BE AROUND 100 TO 200 IF YOU ARE DIRECTLY CONNECTED TO A MAINFRAME
SYSTEM.  iT MAY NEED TO BE LOWER IF YOU ARE ON A bbs.  iT ALL DEPENDS
ON HOW LONG THE REMOTE SYSTEM TAKES TO RESPOND TO A PAUSE SIGNAL.

oN SOME MAINFRAMES, IF YOU DIAL INTO THE SYSTEM WITH YOUR MODEM AT
2400 BAUD OR LESS, YOU MAY FIND THAT PAUSE SIGNALS WON'T HAVE ANY
EFFECT AT ALL, AND FLOW CONTROL DOES NOT WORK.  tHIS IS BECAUSE THE
MAINFRAME SYSTEM IS SENDING DATA AS FAST AS IT MAY INTO ITS MODEM'S
BUFFER, AND ITS MODEM IS EMPTYING ITS BUFFER AT THE SLOWER BAUD RATE.
tHEREFORE, THE MAINFRAME IS ALREADY WAITING AT THE PROMPT WHILE ITS
MODEM SENDS DATA.  tO CORRECT THIS SITUATION, YOU MUST FIND SOME WAY
TO SLOW DOWN THE MAINFRAME TO THE SPEED OF YOUR CONNECTION.

yOUR MILEAGE WILL VARY WITH FLOW CONTROL.  wITH SOME CONNECTIONS IT
WORKS FLAWLESSLY, WHILE ON OTHERS YOU MAY STILL LOSE CHARACTERS.  iF
FLOW CONTROL DOES NOT WORK WELL ENOUGH FOR YOU ON A PARTICULAR SYSTEM,
YOU MAY TRY 80 COLUMN SCROLL ADJUST (SEE 3.1.2, cOMMODORE KEY
COMMANDS, c= w).

3.5.26  tRANSFER TRANSLATION.

iF YOU ARE DOWNLOADING A SEQUENTIAL FILE (TEXTFILE) FROM A BULLETIN
BOARD, IT MAY BE IN STANDARD ascii.  iN ORDER TO CHANGE THE FILE TO
petscii WHILE IT IS DOWNLOADED, YOU MAY TURN THIS OPTION ON.  tHIS
CAUSES THE INCOMING FILE TO BE TRANSLATED THROUGH THE ascii RECEIVE
TRANSLATION TABLE IN MEMORY BEFORE IT IS SAVED TO DISK.  sIMILARLY, IF
THIS IS TOGGLED ON WHEN YOU UPLOAD A FILE, THE FILE IS TRANSLATED
THROUGH THE TRANSMIT TABLE BEFORE IT IS SENT TO THE RECEIVING
COMPUTER.

3.5.27  cHOP x/yMODEM PADDING.

wHEN YOU DOWNLOAD A FILE USING xMODEM, xMODEM-1K, OR yMODEM BATCH, THE
LAST BLOCK IS PADDED WITH CONTROL-z CHARACTERS TO INCREASE ITS SIZE TO
THE REQUIRED 128 OR 1024 BYTES.  tHIS LEAVES EXTRA BYTES AT THE END OF
THE FILE WHEN IT IS SAVED.  iF YOU HAVE THIS OPTION TURNED ON, THESE
PADDING BYTES AT THE END OF THE FILE ARE STRIPPED, BRINGING THE FILE
BACK TO ITS ACTUAL LENGTH.  tHIS COULD CORRUPT A BINARY FILE WHICH HAS
CONTROL-z CHARACTERS AT ITS END, BUT SUCH FILES ARE UNCOMMON.

3.5.28  sWIFTlINK.

tHE sWIFTlINK CARTRIDGE MAY BE MAPPED TO THREE DIFFERENT MEMORY
LOCATIONS.  tHIS MAY BE NECESSARY IF YOU HAVE SOME OTHER DEVICE HOOKED
UP TO THE CARTRIDGE PORT THAT USES sWIFTlINK'S DEFAULT MEMORY
LOCATION.  cONSULT THE sWIFTlINK DOCUMENTATION FOR MORE INFORMATION
ABOUT CHANGING THE MAPPING WITHIN THE CARTRIDGE ITSELF.

wHEN YOU SELECT THIS OPTION, YOU ARE GIVEN A MENU OF THREE AREAS OF
MEMORY.  sELECT THE AREA OF MEMORY THAT YOUR CARTRIDGE IS MAPPED TO.
tHE DEFAULT IS $de00, WHICH SHOULD BE USED IF YOU HAVE NO OTHER
SPECIAL DEVICES HOOKED UP.  yOU MAY MAP THE sWIFTlINK TO $df00 AND
$d700 AS WELL. mAPPING TO $d700 IS ONLY POSSIBLE WITH A cOMMODORE 128
IN 64 MODE.